Add a status update and more about getting to RFC #237
Conversation
Particularly since two of the four drafts are expired right now, and at the current rate we probably won't quite manage to publish another round before the other two expire, it seems like a good idea to make it very clear that the project is active. That should soon be apparent from PRs, but it's been a bit slow over the summer.
|
Thanks for this. Regarding path to standardisation: The JS Foundation might be able to allow us access to the W3C. Of course, it would likely be a HUGE amount of effort to re-encode the standard in W3C format... possibly prohibitivly so. I just though, I don't know if you want to state that it WILL be IETF, or just that's our (hopefully) most likely situation. |
|
@Relequestual since you approved this and I don't hear any outright objection in your comment, I'm merging it as-is. Please feel free to rework the text around possible paths to standardization. I tried not to preclude any option, but also didn't want to have really nebulous stuff out there. |
|
That's fine by me. I think it's still preferable to look towards the IETF route. |
Particularly since two of the four drafts are expired right now,
and at the current rate we probably won't quite manage to publish
another round before the other two expire, it seems like a good
idea to make it very clear that the project is active.
That should soon be apparent from PRs, but it's been a bit
slow over the summer.